--------------------------------------------
   ProLink LoRaWAN Firmware EU868 release_notes.txt
   2026 IMST GmbH
--------------------------------------------


.1 Content:
----------------------------------------------------------------------------------------------------------
This file contains an overview about the most important feature updates and bugfixes 
----------------------------------------------------------------------------------------------------------

.2 Supported Hardware
--------------------------------------------------------------------------
- iM891A-XL  Module     : ProLink_LoRaWAN_EndNode_Modem_EU868_iM891A_XL_Vx_y.hex
- iU891A-XL  USB Stick  : ProLink_LoRaWAN_EndNode_Modem_EU868_iU891A_XL_Vx_y.hex

.3 Revision History:
--------------------------------------------------------------------------
27.08.2026 - Release V3.0 / Build Count 45
     - Bugfix related to RFU parameters, e.g. LinkADRReq (update in LoRaWAN certification testing)
     - Fix related to NewChannelReq (LoRaWAN spec not clear)
       (NewChannelReq rejected if it modifies the only available channel for the desired configuration, which would stop further transmissions)

06.02.2025 - Release V1.0 / Build Count 41
    - Bugfix: Duty Cycle implementation and LoRa proprietary communication for 7.8 kHz bandwith updated
    - HCI update: configuration of parameters only available for the selected stack (LoRaWAN/LR-Base)
    - RP002-1.0.3: Regional Parameters document followed

09.09.2024 - Release V1.0 / Build Count 31
    - First Release with iM891A-XL/iU891A-XL support
   
.4 Known Limitations
-----------------------------------------------------------------------------------------------------------
- Activation By Personalization only available for testing purposes
- Following limitations related to the time synchronization:
* GPS epoch time used to synchronize the time on the end-device.
Note that there is a small time different between the GPS epoch and the UTC time. 
Moreover, the configuration of the time zone is not available, so that no correction is performed. 
* The time synchronization is performed if the DeviceTimeAns is received in any unicast class A/C downlink.
This means, that a time synchronization is performed even if the end-device does not send any request.